Execution engine

ABSTRACT

The execution engine is a new organization for a digital data processing apparatus, suitable for highly parallel execution of structured fine-grain parallel computations. Possible applications include many types of digital signal processing computations, such as filtering, convolution, and deconvolution, as well as many types of linear algebra operators, such as iterative and direct solvers, singular value decomposition, and constraint optimization. The invention improves energy efficiency of these structured parallel operators as compared to a regular data flow or von Neumann computer.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/130,114, filed May 27, 2008 and entitled “EXECUTION ENGINE”; which is hereby incorporated by reference in its entirety for all purposes.

FIELD OF THE INVENTION

The present invention relates to the field of computer systems, and in particular to the efficient execution of fine-grained parallel instructions.

BACKGROUND OF THE INVENTION

A typical general purpose computer is configured as a sequential instruction stream processor, which fetches instructions from memory, decodes, and executes these instructions. The sequential instruction stream processors use energy very inefficiently with more energy consumed in the instruction management than in the actual execution of the operation that the instruction represents. For example, modern general purpose x86 processors from Intel or AMD only attain 10% of peak performance as measured by the operational throughput of the processor on important algorithms such as sparse matrix solvers.

Furthermore, these sequential instruction stream processors are very inefficient for fine-grained parallel computation. In the aforementioned sparse matrix solver, performance requirements typically require that thousands of processors are used concurrently. To coordinate execution among groups of processors, much time and energy is wasted when some processors finish before others and subsequently need to wait to synchronize with the rest of the processors.

The algorithms for which the general purpose computer is becoming less and less efficient are of vital importance to science, engineering, and business. Furthermore, the exponential growth of data and computational requirements dictates that groups of processors are used to attain results in a reasonable amount of time. Many of the important algorithms such as signal processing, solvers, statistics, and data mining, exhibit fine-grained parallel structure. Mapping these algorithms on networks of general purpose processors is becoming problematic in terms of size, cost, and power consumption.

SUMMARY OF THE INVENTION

The present invention is an apparatus for the efficient execution of highly parallel fine-grain structured computations. The apparatus is programmable to perform efficient execution on a wide variety of such structured computations. Energy consumption in a computer is proportional to the number of instructions executed and data operands needed. In an electronic implementation of a computer, this implies that energy consumption is proportional to time and distance instructions and data need to travel. This invention generates a physical model of execution that honors spatial distances and the invention organizes the computation in such a way that contention among instructions is managed through a simple queuing system.

An apparatus in accordance with the present invention includes a processing element that receives data tokens from a fabric of processing elements and matches these to instruction tokens on the basis of a spatial tag. This tag creates spatial relationships between computations to reflect energy and temporal optimizations the algorithmic designer intended.

In some embodiments, the processing element fabric is supplied data tokens from a bank of data streamers, which transform data structures that are stored in computer memory into a stream of data tokens.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be understood with reference to the following drawings in which like elements are indicated by like numbers. These drawings are provided to illustrate selected embodiments of the present invention and are not intended to limit the scope of the invention.

FIG. 1 is a block diagram of a generalized data flow computer system that operates according to some embodiments.

FIG. 2 is a block diagram of a data streamer according to some embodiments.

FIG. 3 is a block diagram of the processor fabric according to some embodiments.

FIG. 4 is a block diagram of the processing element according to some embodiments.

FIG. 5A demonstrates one particular embodiment of a data packet.

FIG. 5B demonstrates one particular embodiment of a data token.

FIG. 5C demonstrates one particular embodiment of the instruction token.

FIG. 6. is a block diagram of one particular embodiment of the instruction store.

FIG. 7A is an example of a single assignment form program for matrix-vector multiplication.

FIG. 7B shows the associated single assignment graph in two dimensions.

FIG. 8 illustrates a flowchart of a method of utilizing an execution engine.

DETAILED DISCUSSION OF THE INVENTION

The following discussion sets forth numerous specific details to provide a thorough understanding of the invention. Those of ordinary skill in the art having the benefit of this disclosure will appreciate that the invention may be practiced without these specific details. Various well known methods, procedures, components, and circuits have not been described in detail in order to focus attention on the features of the present invention.

An execution engine executes single assignment programs with affine dependencies. Programs in single assignment form (SAF) are algorithms that express the computation as a set of equations where each assignment refers to a unique identifier. Typical expressions of single assignment programs are recurrence equations where the left hand side is interpreted as a unique identifier. Many algorithms have natural expressions in single assignment form. For example, FIG. 7A shows an example of a single assignment program for matrix-vector multiplication. FIG. 7B demonstrates the associated single assignment graph, which is a data flow graph where nodes represent computations and edges represent data movement.

Any program is able to be expressed in single assignment form. Programs with fine-grain structured parallelism are most naturally expressed in single assignment form because single assignment form algorithms are maximally parallel formulations that do not have any explicit sequencing to schedule execution. This allows the execution environment to focus on how to manage resource contention. A program in single assignment form contains a unique assignment for each operation. This is able to be represented by a single assignment graph (SAG) that contains a node for every operation and an edge for every data movement. A computational event is defined as some operation taking right hand side operands and computing the assignment on the left hand side of the equation.

Because of the limited speed of signal propagation, any two concurrent computational events are separated either in time or in space. By embedding a single assignment form program in an abstract lattice, defined as a discrete subgroup of RN that spans it as a real vector space, an algorithm designer is able to specify spatial distance between dependent computations. In some embodiments, the embedding is accomplished in an abstract orthonormal lattice. An orthonormal lattice is defined by an orthonormal basis; all basis vectors have unit length, and their inner products are zero. The single assignment graph is able to be embedded in the lattice with the rule that no dependent computational events are able to reside at the same lattice point. This will assign each computational event a/unique location in the lattice and separate dependent computations by physically separated lattice points, thus making explicit the temporal separation for communicating the dependent operands. This unique location in the lattice is called the signature of the computational event, and it is defined as the index vector identifying the lattice point in the lattice. Other examples of appropriate lattices would be crystal groups and other discrete samplings of space that are defined by some regular cell that generates a cover of space. There are well defined mathematical structures describing these samplings called lattice groups. Orthonormal lattices are a subset of these more general lattice groups.

After embedding the SAG in some lattice, all program inputs and all computational events have an explicit routing vector that defines how results are delivered to the dependent computational events. This routing vector is called the dependency vector since it specifies how computational instructions depend on their inputs. The embedding in a spatial lattice allows the algorithm designer to incorporate constraints such as distance and resource contention. Distance is very important for power efficiency and performance since both energy consumption and time to communicate a dependent operand is directly proportional to distance. Distance here is defined in terms of hops in a discrete routing network so each hop needs to go through at least one register thus consuming energy proportionally to the number of hops.

The execution engine described herein is an efficient execution engine for above-mentioned embedded single assignment programs embedded in an abstract spatial lattice.

Referring first to FIG. 1, there is shown a block diagram of a generalized data flow computer system that operates according to some embodiments. The computer system 100 includes a memory 110 that contains the data and the program to execute. The memory 110 is able to be any applicable type of memory. Execution starts by the controller 120 requesting a program from the memory 110. The controller 120 presents a read request via bus 121 to the memory controller 130 which translates the read request to a memory request and returns the data to the controller 120. This data contains the program instructions to execute a single assignment program. The controller 120 decodes these program instructions and translates them into programming information for the streamers 140, and are delivered to the streamers 140 via a control bus 122. Concurrently, the controller 120 sends programming information for the processor fabric 160 through a command bus 123 to the crossbar 150. The crossbar 150 delivers the programming information including commands to the proper rows and columns of the processor fabric 160 which reads these commands and configures itself to execute the single assignment program. Once the overall data path is set up, the controller 120 issues an event to the streamers 140 to start. The memory controller 130 receives read and write requests from the streamers 140 and transforms them into memory requests. On read requests from the streamers 140, data is delivered by the memory controller 130 to the streamers 140 and forwarded to the crossbar 150. The crossbar 150 routes the data streams to the appropriate rows or columns in the processor fabric 160. The processor fabric 160 receives the incoming data streams, executes instructions on these streams and produces output data streams. These output data streams are written back to memory 110 by traversing the crossbar 150 to the streamers 140 that associate memory addresses to the data streams, and then present them to the memory controller 130, which will write the data streams into memory 110. Once the streamers identify completion of the computational task, notifier events are sent back to the controller 120 via the control bus 122. Command/event buses 123 and 124 are used to communicate interrupts and other events back to the controller 120 to signal errors, panics, and operational information that the controller is able to use to interrupt or otherwise steer the computation.

Referring now to FIG. 2, there is shown a block diagram of a data streamer 140. A data streamer executes a stream program that assembles and/or disassembles a data token stream. The process starts by the controller 120 decoding a single assignment program and transforming this program into stream programs for the streamers 140. The controller 120 writes this stream program to the stream program store 220 via a control bus 122. A stream program details how to calculate request addresses and other attributes such as size and type. The stream program is executed by the processor 210. The processor 210 executes the stream program and produces memory controller commands which are written into the command data queue 250. As part of the same stream program, processor 210 also produces the associated token attributes recurrence identifier, signature, and data type. Those attributes are consumed by the token assembly unit 230, which combines these attributes with read data that is coming from the memory controller 130, to produce a data token stream that is written to the cross bar 150. Similarly, for data streams that come from the crossbar 150 and that need to be written back to memory, the token disassembly unit 240 strips the token attributes recurrence identifier, signature, and data type from the incoming data token and writes them in the stream program store 220 for further processing by the processor 210. The token disassembly unit 240 writes the data payload of the data token into the write data queue 270. Concurrently, the processor 210 executes a write stream program to generate the proper memory write commands which are, with the write data, presented to the memory controller 130.

Referring now to FIG. 3, the crossbar 150 provides an interconnection network to connect N data streamers to M processing elements (PE) 310 in the processor array. The streamers 140 transform a flat data structure in memory into a multidimensional data stream in time. The crossbar 150 connects the physical position of any streamer to one, many, or all physical positions of the processing elements in the processor fabric 160. The processor fabric 160 consumes these multidimensional data streams and connects them together inside the fabric under the control of the single assignment program that controller 120 read from memory and installed in the processing elements of the processor fabric through an instruction token stream written on bus 123 that uses the crossbar 150 to connect to the appropriate processing elements 310. The multidimensional data streams flow through the processing elements 310 and the processing element routing network 320. The PEs 310 process instruction and data tokens. Instruction and data tokens are able to be routed and stored in the PE 310. The single assignment program describes how data tokens combine in some multi-dimensional space. The PEs 310 recognize the spatial tag called the signature of a computational event and take action under control of the single assignment program installed in their program store by controller 120. The action is to compare the signature of an incoming data token with the signatures of instruction tokens that accumulate in the PEs 310 during execution, and extract the data token from the internal network 320 if there is a match. The overall computation represented by the single assignment program evolves as the multi-dimensional data streams match up within the processing elements 310 and producing potentially new multi-dimensional data streams, representing intermediate results, which are propagated through the routing network 320 to their computational event destination in the processor fabric. Final result data streams are streamed back to the crossbar 150 via the routing network 320 and the PEs 310 under the control of the single assignment program stored in the PEs 310. The crossbar 150 presents these data streams back to the appropriate streamers 140 which transform them into flat data structures again that are able to be written to memory 110. During the execution of the single assignment program error conditions are able to occur, or it may be of interest to observe processing events so that the controller 120 is able to better manage the computation. Examples of program errors are floating point exceptions like underflow or overflow, instruction exceptions like division by zero, or panic events like resource depletion or time outs. Because, the routing network 320 is able to be negatively affected by such conditions and to provide better guarantees for delivery and handling of critical events, there is a separate communication network 330 for such events that is connected by a bidirectional bus 124 to the controller 120. The bidirectional event bus 124 is used by the processor fabric 160 and the controller 120 to collect, aggregate, and steer the computation that is evolving inside the processor fabric 160.

The structure of the processing element 310 is depicted in FIG. 4. Before the start of a computation in the processor fabric 160, the controller 120 writes control information regarding the single assignment program into the PE's program store 440. The information written into the program store 440 includes an identifier to disambiguate recurrence equations, a domain of computation on which the recurrence equation is active, a signature update program, and a routing vector. The domain of computation is a specification, typically a constraint set defined by a system of inequalities. An example of such a constraint set is {(i,j)|1≦i,j≦N}. This would be the domain of computation of the recurrence equation shown in FIG. 7. This constraint set is a system of four inequalities:

1. i≧1 2. j≧1 3. i≦N 4. j≦N

This system of inequalities can be described by the following matrix:

${\begin{pmatrix} {- 1} & 0 & 1 & 0 \\ 0 & {- 1} & 0 & 1 \end{pmatrix}\begin{pmatrix} i \\ j \end{pmatrix}} \leq \begin{pmatrix} {- 1} \\ {- 1} \\ N \\ N \end{pmatrix}$

This constraint matrix and right hand side vector can be used as the normalized form to specify the constraint set for some embodiments. This program information is delivered to the PEs 310 through control packets that are injected into the processor fabric 160 by the controller 120. The port arbiter 410 of each PE 310 receives packets from the routing network 320. The port arbiter 410 selects one or more packets from the network ports of file PE 310 and forwards these packets to the packet decoder 420. The packet decoder 420 inspects the packet to determine if it contains programming or other type of control information. If the packet is a control packet, the packet decoder 420 sends the packet to the controller 430 which extracts the control information and programs the different elements of the data path, in particular, the program store 440 and the instruction store 450. The control and status information is written via the control bus 431. The program store 440 will receive for each recurrence equation that is part of the single assignment program, an identifier, a specification of a domain of computation, a signature update specification, and a routing vector. This information defines some affine recurrence equation which the PE 310 will help execute. In general, the recurrence equation executes on multiple PEs 310, so it is more natural to state that the recurrence equation executes on the processor fabric 160. After the controller 120 is done programming the processor fabric 160, execution is able to commence. The execution starts with the data streamers 140 injecting the first data packets into the processor fabric 160 (via the crossbar 150). When data packets arrive on network ports of a PE 310, the packet arbiter 410 selects one or more packets and forwards them to the packet decoder 420. The packet decoder 420 inspects the packet to determine if it is a data packet that belongs to a computation that executes on that particular PE 310. If it does, the packet decoder 420 extracts the routing vector of the packet. If the routing vector is not null, the packet decoder 420 forwards the packet to the packet router 425. The packet router 425 computes the next leg in the route, updates the routing vector of the packet, and presents the updated packet to the port arbiter 410 to be injected back in the routing network 320. If the routing vector is null then the packet decoder 420 sends the data token to the instruction store 450. The instruction store 450 extracts the instruction tag from the data token and assigns the data payload to the appropriate operand slot in the associated instruction stored and pending in the instruction store 450, or it allocates a new instruction if this is the first data token received for this particular computational event. When a pending instruction has received all its operands, the instruction store 450 will deallocate the instruction from the pending instruction list and queue the instruction token for execution by sending it to the token disassembly unit 460. The instruction token includes the instruction opcode, the variable identifier of the recurrence equation, the signature of the computational event this instruction represents, and the constituent operands. The token disassembly unit 460 extracts the signature from the instruction token, and sends the signature with the variable identifier to the signature pipeline 470. The signature pipeline 470 looks up the variable identifier in the program store 440 to retrieve the signature update program to apply to the signature. The signature update program is a simple affine transformation on the incoming signature, which as indicated in the general description section, is able to be interpreted as a spatial index vector in some abstract lattice. The signature pipeline 470 applies this affine transformation to the incoming signature to produce a new signature. This new signature is forwarded to the token assembly unit 490. Concurrently with the execution of the signature pipeline, the value pipeline 480 executes the instruction to generate a new left hand side value. The token disassembly unit 460 extracts the instruction opcode and operands from the instruction token and forwards that to the value pipeline 480. The value pipeline 480 executes the instruction and forwards the result to the token assembly unit 490. The token assembly unit 490 takes the output of the signature pipeline 470 and the output of the value pipeline 480 and constructs a new data token. It checks the signature of this new data token against the domain of computation for this recurrence equation, and if inside the domain, it sends the data token to the packet router 425. If the routing vector is not the null vector, the packet router 425 embeds the data token into a packet and forwards that to the port arbiter 410 to be injected back into the routing network 320 under the control of some arbitration policy. Examples are first-come-first-served, or priority based schemes to implement quality-of-service guarantees. If the routing vector of the data token is null, it implies that the data token is recirculating inside the current PE 310 and the packet router 425 sends the data token to the instruction store 450 where it is matched up with an instruction.

Referring to FIG. 5A, there is shown one possible embodiment of the structure of data packets 510 flowing through the routing network 320. Data packets 510 flow through the routing network to deliver data values to the PEs 310. In this embodiment, the data packet 510 includes a packet identifier 511, a queue identifier 519, a stream identifier 512, a recurrence equation identifier 513, a data type 514, a signature 515, a data value 516, and a routing vector 517. The packet identifier 511 is a debug feature to help identify any computational errors. During the execution of a single assignment program on the fabric, thousands of packets are able to be in the system at any point in time. To be able to identify a specific packet in this collection requires that a unique identifier is carried. This information would be akin to debug information and instructions that are injected in the instruction stream of an instruction stream processor by its compiler to help debug functional problems in the code. During execution of release code, this unique packet identifier would not be part of the data packet.

Still referring to FIG. 5A, this exemplary data packet 510 is able to be used in a 2-dimensional processor fabric executing 4-dimensional single assignment programs. The 2 dimensional processor fabric would determine that the routing vector 517 is 2-dimensional and represents a Manhattan route to the destination PE 310. As described in the operation of the PE 310 a non-null routing vector would be detected by the packet decoder 420 and forwarded to the packet router 425 to be routed to the next PE 310 in the route. The 4-dimensional single assignment program would manifest itself in the signature 515 to be a 4-vector representing the 4 indices of 4-dimensional space. The signature 515 combined with the recurrence identifier 513 are very important in program execution according to the present invention. The recurrence identifier 513 and signature 515 uniquely identify one computational event in the single assignment program. The result of that computational event is stored in the data value slot 516, and its type is identified by the data type 514. To deliver the result to the next computational event it participates in, the network routes the data packet via the routing vector 517, and uses the queue identifier 519 to help the packet routers 425 in the PEs 310. Each recurrence equation gets assigned a unique queue ID by the compiler, which enables the packet routers to quickly queue incoming data packets with minimum decode hardware. Given the fact that in a fully active 2D routing mesh there are four concurrent incoming packets, the pressure on the front-end of the PE 310 is significant. By carrying some of the queue information in the data packet, the hardware complexity of the packet router in the PE 310 is reduced. Finally, the stream identifier 512 is used to associate a data packet to a flat memory data structure. When the data streamers 140 generate multidimensional data streams from a flat memory data structure, the signature identifies the location within the data structure but the stream identifier 512 is needed to identify the data structure. This is akin to base addresses used in instruction stream processors where the program that executes on a memory data structure is specified relative to a base address. The stream identifier 512 enables the data streamers to properly identify where the data packet comes from and where it is going to in memory.

Now referring to FIG. 5B, there is shown one possible embodiment of the structure of a data token 520 that would be used with the data packet depicted in FIG. 5A. Data tokens 520 carry the minimum information needed for the instruction store 450 to identify which instruction this data element belongs to. As is able to be seen by comparing FIG. 5A and FIG. 5B, the data token 520 is completely contained within the data packet 510. The individual fields in the data token are the same fields as described in the data packet description above. This is a common structure among different embodiments since the data packets are really routing mechanisms to deliver data tokens throughout the processor fabric 160. By using the same structure between data packets and data tokens, the data tokens are able to be quickly assembled and disassembled, which reduces hardware complexity and improves performance both in terms of power as well as throughput and latency. The structure of the data token determines the detailed operation of the instruction store 450, which in many ways is able to be seen as the core control mechanism that enables execution of arbitrary single assignment programs arising from systems of affine recurrence equations. The instruction store 450 organizes data tokens and assembles and organizes instruction tokens pending execution. The instruction store 450 embodiment that belongs with the data token structure 520 as depicted in FIG. 5B is shown in FIG. 6.

Referring to FIG. 6, data tokens arrive at the data token disassembly unit 610. The data token disassembly unit 610 extracts the different fields of the data token. To identify the instruction to which this data token must be delivered, the data token disassembly unit 610 extracts the recurrence identifier 513 and the signature 515 from the data token and sends that to a lookup unit 620. The lookup unit 620 queries the program store 440, shown in FIG. 4 to retrieve the instruction information. The lookup unit 620 constructs an instruction tag 625 by simply combining the recurrence identifier 513 and the signature 515. This is a unique identifier for the computational event that this data token participates in. Additionally, the lookup unit 620 also receives information from the program store 440 about the slot location the data token occupies in the instruction. This information controls the slot assignment unit 630, which receives the data type 514 and the raw data value 516 from the data token disassembly unit and routes this to the appropriate slot in the pending instruction. The last function the lookup unit 620 performs is the construction of an instruction header 651, which contains information about how to manage the pending instruction in the pending instruction token store 650. Now referring back to FIG. 5C, there is shown an embodiment of an instruction token that is managed in the pending instruction token store 650. The instruction header 651 includes the instruction opcode 531, the slot cover 532, and the slot occupancy field 533. The instruction opcode 531 is a field that controls the functional units in the value pipeline 480. It encodes the type of operation that needs to be applied to the operands. Examples are the typical functional unit operators such as ADD, MULTIPLY, or DIVIDE, or any logic operations such as MASK, BIT_TEST, or SHIFT. The slot cover field 532 specifies how many operands the instruction requires. For example, for simple instructions, a single input operand is able to be used whereas for more complex instructions, a typical three operand structure is used. The slot cover field 532 and the slot occupancy field 533 work together in the pending instruction token store to determine if an instruction has received all its operands. The process that is used starts with the lookup unit 620 composing an instruction tag 625 and sending it to the tag CAM 640. The tag CAM 640 is a content addressable memory that is addressed by these instruction tags. When the tag CAM 640 indicates a miss, this implies that the instruction has not been yet allocated in the tag CAM 640, and on a miss, the tag CAM 640 will allocate a pending instruction. If the tag CAM 640 indicates a hit, this implies that there is a pending instruction to which the data token is able to be delivered. The tag CAM 640 provides a pointer into the pending instruction token store 650 to the storage associated with this pending instruction. The lookup unit 620 provides the instruction header 651 as previously described, and the slot assignment unit writes the data token value into the appropriate slot in the pending instruction. Furthermore, it will update the slot occupancy field 532 and compare it to the required slot cover 532. If the two are equal, all operands have been received and the instruction is ready for execution. The instruction tag 645 and the pending instruction including fields 651, 534, 535, and 536, are send to the instruction token assembly unit 660, which will construct the instruction token 530 as shown in FIG. 5C. The instruction token assembly unit 660 will forward completed instruction tokens to the execute units, starting with the token disassembly unit 460, as depicted in FIG. 4.

FIG. 8 illustrates a flowchart of a method of utilizing an execution engine. In the step 800, a program is requested from a memory by a controller including presenting a read request to a memory controller which translates the read request to a memory request and returns data to the controller. The data contains program instructions to execute a single assignment program. In the step 802, the program instructions are decoded into programming information and translated and delivered to data streamers. In the step 804, the programming information is sent to a crossbar. In the step 806, the programming information is delivered from the crossbar to a processor fabric. In the step 808, the programming information is read, and the processor fabric is configured to execute the single assignment program. In the step 810, an event is issued from the controller to the streamers to start sending data streams once an overall data path is set up. In the step 812, read and write requests are received from the streamers, and the read and write requests are transformed into memory requests at the memory controller. In the step 814, data streams are routed by the crossbar to rows or columns in the processor fabric for executing instructions on the streams and produces output data streams, wherein the output data streams are written to the memory by traversing to the crossbar to the streamers that associate memory addresses to the data streams and then present the data streams to the memory controller which writes the data streams into the memory. In the step 816, notifier events are sent to the controller once the streamers identify completion of a computational task.

To utilize the execution engine, a user inputs and/or initiates a program to the execution engine, for example if the execution engine is implemented in a computer. The execution engine then executes the program as described above. Depending on the program, the program outputs a desired result. For example, if the user wants to perform a computationally complex mathematical equation, the output after the execution engine executes is the result of the equation.

In operation, by organizing the execution of the single assignment program in the form described herein, the execution engine has solved many problems encountered when using an instruction sequence processor. There is no instruction pointer that guides the execution. The execution engine is completely data driven. When data elements become available they trigger dependent computations. Thus, the execution engine functions like a data flow machine. However, in a data flow machine, there is no spatial structure to take advantage of since the lookup is done on the basis of flat memory addresses. The second problem with the traditional data flow machine is that the CAM that holds the pending instructions needs to be very large to be able to execute a large scale program. Content addressable memories become less power efficient and slower when they become larger. The CAM has been the traditional bottleneck in a data flow machine because it cannot compete on performance with an instruction sequence processor using a von Neumann architecture. The execution engine includes spatial constraints added to the specification of the computation that the architecture honors, and thus energy constraints are able to be be captured in the program. Furthermore, the spatial constraints allow distribution of the CAM across all the processing elements, and thus the architecture scales again in terms of concurrency. As an example, a small instance of the execution engine is able to integrate 4096 processing elements on a single chip. Each instruction store in the processing elements could contain 64 pending instructions for a total concurrency of 262144 instructions in a single chip. Typical concurrency measures in a 4 core chip multi processor are of the order of 100, and even highly parallel 256 processor graphics processing units are limited to concurrency measures of the order of 10000. With the execution engine, the ability to manage vasts amount of concurrency is unparalleled.

The present invention has been described in terms of specific embodiments incorporating details to facilitate the understanding of principles of construction and operation of the invention. Such reference herein to specific embodiments and details thereof is not intended to limit the scope of the claims appended hereto. It will be readily apparent to one skilled in the art that other various modifications may be made in the embodiment chosen for illustration without departing from the spirit and scope of the invention as defined by the claims. 

1. A computing device comprising: (a) a memory for storing data and a program; (b) a controller for requesting the program from the memory; (c) a processor fabric for processing the program; and (d) a crossbar for sending the program to the processor fabric.
 2. The device of claim 1 further comprising a memory controller configured for communicating with the memory.
 3. The device of claim 1 further comprising data streamers configured for sending data streams to the crossbar.
 4. The device of claim 2 wherein the controller is further configured for requesting the program including presenting a read request to the memory controller which translates the read request to a memory request and returns the data to the controller.
 5. The device of claim 4 wherein the data contains program instructions to execute a single assignment program.
 6. The device of claim 1 wherein the controller is further configured for translating the program instructions into programming information and delivering the programming information to the data streamers.
 7. The device of claim 3 wherein the controller is further configured for issuing an event to the streamers to start once an overall data path is set up.
 8. The device of claim 3 wherein the crossbar is further configured for routing data streams to rows or columns in the processor fabric.
 9. The device of claim 8 wherein the processor fabric is further configured for producing output data streams.
 10. The device of claim 9 wherein the output data streams are written to the memory by traversing to the crossbar to the streamers that associate memory addresses to the data streams and then present the data streams to the memory controller which writes the data streams into the memory.
 11. The device of claim 10 wherein the streamers are further configured for sending notifier events to the controller once the streamers identify completion of a computational task.
 12. A computing device comprising: (a) a memory for storing data and a program; (b) a memory controller for communicating with the memory and for receiving read and write requests and transforming the read and write requests into memory requests; (c) a controller for requesting the program and the data from the memory, wherein the data contains program instructions to execute the single assignment program; (d) a processor fabric for processing the program and for producing output data streams. (e) a crossbar for sending the program to the processor fabric; and (f) data streamers for sending data streams to the crossbar.
 13. The device of claim 12 wherein the controller is further configured for translating the program instructions into programming information and delivering the programming information to the data streamers.
 14. The device of claim 13 wherein the controller is further configured for issuing an event to the streamers to start once an overall data path is set up.
 15. The device of claim 14 wherein the crossbar is further configured for routing the data streams to rows or columns in the processor fabric.
 16. The device of claim 15 wherein the output data streams are written to the memory by traversing to the crossbar to the streamers that associate memory addresses to the data streams and then present the data streams to the memory controller which writes the data streams into the memory.
 17. The device of claim 16 wherein the streamers are further configured for sending notifier events to the controller once the streamers identify completion of a computational task.
 18. A method comprising: (a) requesting a program from a memory by a controller; (b) decoding the program to a decoded program; (c) transferring the decoded program to a processor fabric; (d) configuring the processor fabric to execute a single assignment program based on the decoded program; (e) routing data streams to the processor fabric; and (f) executing instructions on the data streams.
 19. The method of claim 18 wherein requesting the program includes presenting a read request to a memory controller which translates the read request to a memory request and returns data to the controller.
 20. The method of claim 19 wherein the data contains program instructions to execute the single assignment program.
 21. The method of claim 20 further comprising translating and delivering the program instructions into programming information to data streamers.
 22. The method of claim 21 further comprising sending the programming information to a crossbar.
 23. The method of claim 22 further comprising issuing an event from the controller to the streamers to start once an overall data path is set up.
 24. The method of claim 23 further comprising receiving read and write requests from the streamers and transforming the read and write requests into memory requests at the memory controller.
 25. The method of claim 24 wherein routing the data streams is by the crossbar to rows or columns in the processor fabric.
 26. The method of claim 25 further comprising producing output data streams.
 27. The method of claim 26 wherein the output data streams are written to the memory by traversing to the crossbar to the streamers that associate memory addresses to the data streams and then present the data streams to the memory controller which writes the data streams into the memory.
 28. The method of claim 27 further comprising sending notifier events to the controller once the streamers identify completion of a computational task.
 29. A method comprising: (a) requesting a program from a memory by a controller including presenting a read request to a memory controller which translates the read request to a memory request and returns data to the controller, the data containing program instructions to execute a single assignment program; (b) decoding the program instructions and translating and delivering the program instructions into programming information to data streamers; (c) sending the programming information to a crossbar; (d) delivering the programming information from the crossbar to a processor fabric; (e) reading the programming information and configuring the processor fabric to execute the single assignment program; (f) issuing an event from the controller to the streamers to start once an overall data path is set up: (g) receiving read and write requests from the streamers and transforming the read and write requests into memory requests at the memory controller; (h) routing data streams from the streamers by the crossbar to rows or columns in the processor fabric for executing instructions on the streams and produces output data streams, wherein the output data streams are written to the memory by traversing to the crossbar to the streamers that associate memory addresses to the data streams and then present the data streams to the memory controller which writes the data streams into the memory; and (i) sending notifier events to the controller once the streamers identify completion of a computational task. 